-
Notifications
You must be signed in to change notification settings - Fork 0
fix(rust/signed-doc): Apply new DocType
#347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
DocType
Signed-off-by: bkioshn <[email protected]>
DocType
DocType
✅ Test Report | |
Signed-off-by: bkioshn <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also could you update proposal.rs
, comment.rs
and submission.rs
tests with applying new doc type ids and also remain at least one test case with the old types.
e.g.
for the proposal.rs
inside test_valid_proposal_doc
, test_valid_proposal_doc_with_empty_provider
and test_invalid_proposal_doc
update "type"
field definition to the new one (as array with multiple values), and also add one more new test test_valid_proposal_doc_old_type
with preserving current test case with the old type definition.
(the same thing do for the comment.rs
and submission.rs
)
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Signed-off-by: bkioshn <[email protected]>
Description
Apply new
DocType
to existingtype
fieldRelated Issue(s)
Closes #328
Breaking Changes
There shouldn't be any breaking change since it should be backward compatible.
Related Pull Requests
#339
Please confirm the following checks